Method of controlling user information and information processing apparatus

ABSTRACT

A method of controlling user information for an information processing apparatus includes the steps of a process of an application program requesting user information controlling unit to obtain an item of said user information, and said user information controlling unit providing the obtained item of said user information to said process. The user information controlling unit obtains the user information requested by the process of the application program and provides the user information to the process. Accordingly, the user information can be shared by the application programs and centrally controlled.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of and is based upon and claims thebenefit of priority under 35 U.S.C. § 120 for U.S. Ser. No. 12/172,694,filed Jul. 14, 2008 which is a divisional of U.S. Ser. No. 10/372,798,filed Feb. 26, 2003, and claims the benefit of priority under 35 U.S.C.§ 119 from Japanese Patent Application No. 2002-050539 filed on Feb. 26,2002, Japanese Patent Application No. 2002-050540 filed on Feb. 26,2002, Japanese Patent Application No. 2002-050547 filed on Feb. 26,2002, Japanese Patent Application No. 2003-039974 filed on Feb. 18,2003, Japanese Patent Application No. 2003-039975 filed on Feb. 18,2003, Japanese Patent Application No. 2003-039976 filed on Feb. 18,2003, Japanese Patent Application No. 2003-039977 filed on Feb. 18,2003, Japanese Patent Application No. 2003-039978 filed on Feb. 18, 2003and Japanese Patent Application No. 2003-039979 filed on Feb. 18, 2003,the entire contents of which are hereby incorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to a method of controlling userinformation and an information processing apparatus, and moreparticularly, to a method of controlling user information in which theuser information is provided to a plurality of application programs, andto the information processing apparatus using the same.

2. Description of the Related Art

An information processing apparatus such as a personal computer and animage forming apparatus can provide users with various informationprocessing functions by executing one or more software programscorresponding to various functions. The information processing apparatusis often connected to other devices via a network and can distributeimage data, for example, to the other devices. The informationprocessing apparatus stores therein user information such asdistribution addresses, user restrictions, and charges.

As an example of the information processing apparatus, an image formingapparatus is a system that functions as a copier, a printer, afacsimile, and a scanner (hereinafter referred to as a multifunctionalapparatus). The multifunctional apparatus is provided with a displayunit, a printing unit, and an image capture unit in the system, and isfurther provided with software programs each corresponding to thefunction of a copier, a printer, a facsimile, or a scanner. A user canuse the multifunctional apparatus as a copier, a printer, a facsimile,or a scanner by switching the software programs.

The image forming apparatus is connected with other image formingapparatuses and computers via a network and distributes the image data,for example, to the other image forming apparatuses and computers. Theimage forming apparatus stores therein user information such asaddresses and user restriction/charges.

The distribution address information is used to manage addressees andsenders. The distribution address information is not so often updated;it is relatively easily backed up. The number of entries is usuallylarge because the addresses of users that do not directly use theinformation processing apparatus or the image forming apparatus areincluded in the distribution address information.

On the other hand, the user restriction information and the chargeinformation are used to manage the authorization (user restriction) ofvarious functions and the usage (the number of printed pages, forexample) of the authorized functions by respective users. The userrestriction/charge information is updated frequently whenever theinformation processing apparatus is used; the creating of its backupcopy is not easy. Only users who directly use the information processingapparatus or the image forming apparatus are managed using the userrestriction/charge information. Therefore, the number of users isrelatively small.

As described above, the distribution address information and the userrestriction/charge information are different in the easiness of backupand the number of users to be managed thereby. Due to this difference,the information storage apparatuses suitable for the respectiveinformation sets are also different. The distribution addressinformation requires an information storage apparatus with a largecapacity even at the sacrifice of speed and reliability. The userrestriction/charge information, however, requires an information storageapparatus of high speed and high reliability at the sacrifice of costand capacity.

Conventionally, an information processing apparatus and an image formingapparatus store the distribution address information in a hard diskdrive, and store the user restriction/charge information in anon-volatile random access memory (RAM).

The conventional information processing apparatus is provided with oneor more application software programs corresponding to each of variousinformation processing functions. Each application program, however,manages the distribution address information separately. Theconventional image forming apparatus is provided with applicationprograms corresponding to user services of intrinsic image formingprocessing such as printing, copying, scanning, and transmittingfacsimile. Each application program, however, manages the distributionaddress information separately.

The separate management of user information thus requires hardwareresources otherwise unnecessary, and increases the risk of bugs in theapplication programs.

Additionally, the distribution address information and the userrestriction/charge information need to be stored and controlled in ahard disk drive (HDD) or a non-volatile random access memory (RAM) sothat the application programs can access these information sets.

A system initialization module and so forth updates the distributionaddress information. When registering, updating, and accessing thedistribution address information or the user restriction/chargeinformation, the system initialization module is required to determinein which, the HDD or the non-volatile RAM, the distribution addressinformation and the user restriction/charge information are stored sothat the system initialization module can designate appropriate one.

Further, in the case of the conventional information processingapparatus and the image forming apparatus, a user is required todirectly operate an operation panel provided on the informationprocessing apparatus and the image forming apparatus to access or updatethe distribution address information and the user restriction/chargeinformation.

Accordingly, the user needs to go to the place where the informationprocessing apparatus and the image forming apparatus are placed in orderto access and update the distribution address information and the userrestriction/charge information.

Additionally, since the size of the operation panels differs, the amountof information displayed on the operation panel changes apparatus byapparatus. The operation panel provided on an image forming apparatus isusually small. Accordingly, depending on the size of the operationpanel, the amount of information that can be displayed on the operationpanel is sometimes not large enough.

Furthermore, the user is required to follow a predetermined format andorder of the information processing apparatus and the image formingapparatus so as to access or update the distribution address informationand the user restriction/charge information.

The user needs to make a substantial effort to directly operate theoperation panel and so forth provided to the information processingapparatus and the image forming apparatus so as to access thedistribution address information and the user restriction/chargeinformation.

SUMMARY OF THE INVENTION

Accordingly, it is a general object of the present invention to providea novel and useful method of controlling user information, and moreparticularly, to provide a method of controlling user information inwhich the user information is centralized and shared by a plurality ofapplication programs.

Another object of the present invention is to provide a method ofcontrolling user information in which the user information can beupdated without designating where the user information is stored.

Yet another object of the present invention is to provide a method ofcontrolling the user information with which the user can easily operatewith little effort.

To achieve one of the above objects, a method of controlling userinformation for an information processing apparatus, according to thepresent invention, includes the steps of a process of an applicationprogram requesting a user information control unit to obtain an item ofsaid user information, and said user information control unit providingthe obtained item of said user information to said process.

The user information control unit obtains the user information requestedby the process of the application program and provides the userinformation to the process. Accordingly, the user information can beshared by the application programs and centrally controlled.

According to another aspect of the present invention, an informationprocessing apparatus includes a plurality of information storage unitsstoring user information, and a user information control unit that, inresponse to a request from a process of an application program, obtainssaid user information from said information storage units and providesthe obtained user information to said process of said applicationprogram.

According to yet another aspect of the present invention, a method ofcontrolling user information for an information processing apparatus,includes the steps of a system initialization module requesting a userinformation control unit to update user information, and said userinformation control unit updating, in response to the request from saidsystem initialization module, said user information.

The user information control unit updates the user information incompliance with the request from the system initialization module.Accordingly, the system initialization module can update the userinformation without designating in which information storage unit theuser information is stored. The user information is centrallycontrolled.

According to yet another aspect of the present invention, an informationprocessing apparatus includes a plurality of information storage unitsstoring user information therein, and a user information control unitthat updates, in response to a request from a system initializationmodule, said user information stored in said information storage unit.

According to yet another aspect of the present invention, a method ofcontrolling user information for an information processing apparatusincludes the steps of a user information control unit receiving arequest in connection with user information from an external controlapparatus connected to said information processing apparatus via anetwork, and said user information control unit processing said requestusing predefined functions.

The user information can be controlled using the external controlapparatus connected to the information processing apparatus via thenetwork. Accordingly, the operator can control the user informationwatching a large screen provided to the external control apparatusinstead of a small operation panel provided to the informationprocessing apparatus. The user can handle the user information flexiblyand easily. The operator does not need to go to the place where theinformation processing apparatus is placed. Additionally, the userinformation can be shared with another information processing apparatus.

According to yet another aspect of the present invention, an informationprocessing apparatus includes a plurality of information storage unitsstoring user information therein, and a user information control unitthat receives a request in connection with said user information storedin the information storage units from an external control apparatusthrough a network and handles said user information using a predefinedfunction corresponding to said request.

According to yet another aspect of the present invention, a computerprogram that causes a computer to control user information includes thesteps of requesting an information processing apparatus connected via anetwork to transmit said user information using a predetermined protocolfor exchanging messages expressed in a description language, receivingsaid user information from said information processing apparatus incompliance with said protocol, displaying a screen based on the receiveduser information, and requesting, in response to a request to updatesaid user information input by a user, said information processingapparatus to update said user information using said protocol.

The computer program can cause a computer to function as the externalcontrol apparatus that can remote control the user information stored inthe information processing apparatus.

Other objects, features, and advantages of the present invention willbecome more apparent from the following detailed description when readin conjunction with the accompanying drawing.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing an information processingapparatus according to an embodiment of the present invention;

FIG. 2 is a schematic diagram showing the hardware structure of theinformation processing apparatus according to an embodiment of thepresent invention;

FIG. 3 is a schematic diagram showing a multifunctional apparatusaccording to an embodiment of the present invention;

FIG. 4 is a schematic diagram showing the hardware structure of themultifunctional apparatus according to an embodiment of the presentinvention;

FIG. 5 is a schematic diagram for explaining a method of controllinguser information according to an embodiment of the present invention;

FIG. 6 is a table showing user restriction/charge information accordingto an embodiment of the present invention;

FIG. 7 is a table showing distribution address information according toan embodiment of the present invention;

FIG. 8 is a schematic diagram for explaining an accessing operation touser information according to an embodiment:

FIG. 9 is a flow chart showing an accessing operation to distributionaddress information according to an embodiment;

FIG. 10 is a schematic diagram showing a tag set and tags according toan embodiment;

FIG. 11 is a schematic diagram showing tag entries according to anembodiment;

FIG. 12 is a schematic diagram showing an entry selection screenaccording to an embodiment;

FIG. 13 is a flow chart showing the obtaining operation in step S110 ofFIG. 9 according to an embodiment;

FIG. 14 shows an example of API for obtaining configuration informationaccording to an embodiment;

FIG. 15 is a schematic diagram showing the data structure ofconfiguration information according to an embodiment;

FIG. 16 is a flow chart showing the registering operation in step S111of FIG. 9 according to an embodiment;

FIG. 17 shows an example of an API for registering functions to be usedaccording to an embodiment;

FIG. 18 is a flow chart showing the obtaining operation of tag setinformation and tag information in step S112 of FIG. 9 according to anembodiment;

FIG. 19 shows an example of an API for obtaining a tag set according toan embodiment;

FIG. 20 is a schematic diagram showing the tag set data structureaccording to an embodiment;

FIG. 21 shows an example of an API for obtaining tag informationaccording to an embodiment;

FIG. 22 is a schematic diagram showing the data structure of taginformation according to an embodiment;

FIG. 23 is a flow chart showing an obtaining operation of tag entries instep S113 of FIG. 9 according to an embodiment;

FIG. 24 shows an example of an API for obtaining tag entries accordingto an embodiment;

FIG. 25 is a schematic diagram showing the data structure of tag entriesaccording to an embodiment;

FIG. 26 is a flow chart showing an inputting operation of an entry indexnumber according to an embodiment;

FIG. 27 shows an example of an API for obtaining entry control numbersbased on entry index numbers according to an embodiment;

FIG. 28 shows an example of an API for obtaining tags to which a tagentry is attached based on an entry control number according to anembodiment;

FIG. 29 shows an example of an API for obtaining entry positionaccording to an embodiment;

FIG. 30 shows an example of an API for obtaining mail informationaccording to an embodiment;

FIG. 31 shows an example of an API for obtaining sender authenticationinformation according to an embodiment;

FIG. 32 shows an example of an API for obtaining user restrictioninformation according to an embodiment;

FIG. 33 shows an example of an API for obtaining e-mail groupinformation according to an embodiment;

FIG. 34 shows an example of an API for searching entries according to anembodiment;

FIG. 35 is a schematic diagram for explaining the operation of a screencreating module according to an embodiment;

FIG. 36 is a schematic diagram for explaining an updating operation ofthe user information according to an embodiment;

FIG. 37 is a flow chart showing an updating operation of distributionaddress information according to an embodiment;

FIG. 38 is a schematic diagram showing a system initialization menuscreen according to an embodiment;

FIG. 39 is a schematic diagram showing an entry information updatescreen according to an embodiment;

FIG. 40 is a schematic diagram showing an entry information registrationscreen according to an embodiment;

FIG. 41 shows an example of an API for adding a new entry according toan embodiment;

FIG. 42 shows an example of an API for setting a tag to which an entryis attached according to an embodiment;

FIG. 43 shows an example of an API for setting a usercode according toan embodiment;

FIG. 44 shows an example of an API for setting a mail address accordingto an embodiment;

FIG. 45 shows an example of an API for checking and obtaining an indexnumber according to an embodiment;

FIG. 46 shows an example of an API for obtaining groups to which anentry is included according to an embodiment;

FIG. 47 shows an example of an API for updating an entry according to anembodiment;

FIG. 48 shows an example of an API for deleting an entry according to anembodiment;

FIG. 49 shows an example of an API for updating a tag according to anembodiment;

FIG. 50 shows an example of an API for moving the position of a tagentry according to an embodiment;

FIG. 51 shows an example of an API for setting sender authenticationinformation according to an embodiment;

FIG. 52 shows an example of an API for setting a mail group according toan embodiment;

FIG. 53 shows an example of an API for obtaining the number ofregistered entries according to an embodiment;

FIG. 54 is an example of an API for obtaining the number of registeredaccounts according to an embodiment;

FIG. 55 is an example of an API for obtaining the number of registeredgroups according to an embodiment;

FIG. 56 is an example of an API for obtaining the number of registeredmail addresses according to an embodiment;

FIG. 57 is an example of an API for obtaining the number of registeredusercodes according to an embodiment;

FIG. 58 is a schematic diagram for explaining a method of controllingthe user information according to an embodiment of the presentinvention;

FIG. 59 is a schematic diagram for explaining the remote control of theuser information according to an embodiment;

FIGS. 60A-60C show an example of a web service description in compliancewith WSDL according to an embodiment;

FIG. 61 is a flow chart showing an accessing operation of the userinformation using the remote control according to an embodiment;

FIG. 62 shows input/output parameters used in a web service forobtaining configuration information according to an embodiment;

FIG. 63 shows the data structure of the configuration informationaccording to an embodiment;

FIG. 64 shows input/output parameters used in a web service forauthenticating a user or an administrator;

FIG. 65 shows input/output parameters used in a web service forobtaining a generation number;

FIG. 66 shows input/output parameters used in a web service forobtaining a tag set;

FIG. 67 shows the data structure of a tag set according to anembodiment;

FIG. 68 shows input/output parameters used in a web service forobtaining a tag according to an embodiment;

FIG. 69 shows the data structure of tag information according to anembodiment;

FIG. 70 shows input/output parameters used in a web service forobtaining tag entries according to an embodiment;

FIG. 71 shows an example of filter according to an embodiment;

FIG. 72 shows the data structure of an entry according to an embodiment;

FIG. 73 shows input/output parameters used in a web service forobtaining account information according to an embodiment;

FIG. 74 shows the data structure of an account according to anembodiment;

FIG. 75 shows the data structure of mail address information accordingto an embodiment;

FIG. 76 shows the data structure of facsimile number informationaccording to an embodiment;

FIG. 77 shows the data structure of usercode information according to anembodiment;

FIG. 78 shows input/output parameters used in a web service forobtaining group information according to an embodiment;

FIG. 79 shows the data structure of group information according to anembodiment;

FIG. 80 shows the data structure of mail group information according toan embodiment;

FIG. 81 shows the data structure of facsimile group informationaccording to an embodiment;

FIG. 82 shows input/output parameters used in a web service fordisplacing tags in a tag set according to an embodiment;

FIG. 83 shows input/output parameters used in a web service fordisplacing entries in a tag according to an embodiment;

FIG. 84 shows input/output parameters used in a web service for deletingentries having a designated Id number according to an embodiment;

FIG. 85 shows input/output parameters used in a web service for adding anew account according to an embodiment;

FIG. 86 shows input/output parameters used in a web service for updatingaccount information according to an embodiment;

FIG. 87 shows input/output parameters used in a web service for adding anew group according to an embodiment;

FIG. 88 shows input/output parameters used in a web service for updatinggroup information according to an embodiment;

FIG. 89 is a flow chart showing a restoring operation of the userinformation using the remote control according to an embodiment;

FIG. 90 shows input/output parameters used in a web service forprocessing before restoring according to an embodiment;

FIG. 91 shows input/output parameters used in a web service forprocessing after restoring according to an embodiment; and

FIG. 92 is a schematic diagram showing a screen according to anembodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The preferred embodiments of the present invention will be described indetail by reference to the drawings.

FIG. 1 is a schematic diagram showing an information processingapparatus according to an embodiment of the present invention. Theinformation processing apparatus 1000 includes hardware resources 1100and software programs 1200.

The hardware resources 1100 include a memory unit 1110, an input unit1120, a display unit 1130, and other hardware resources 1140. Thesoftware programs include application programs 1210-1 through 1210-n, OS1230 such as UNIX (trade mark), BIOS 1240, device drivers 1250, a userinformation control unit 1260, a communication control unit 1270, and soforth.

When the power is turned on, the information processing apparatus 1000reads OS 1230 from a secondary storage unit to the memory unit 1110, andexecutes the OS 1230. When the power is turned on or an instruction isgiven from an operator, the information processing apparatus 1000 readsan application program 1210-1 through 1210-n from the secondary storageunit to the memory unit 1110, and executes the read application program1210-1 through 1210-n.

The application programs 1210-1 through 1210-n cause the informationprocessing apparatus 1000 to perform various information processingoperations. BIOS 1240 is a computer program that controls the hardwareresources 1100. The device drivers 1250 are computer programs that driveperipheral devices included in the hardware resources 1100.

OS 1230, the user information control unit 1260, and the communicationcontrol unit 1270 communicate with the application programs 1210-1through 1210-n via application program interface (API) 1220. API 1220includes predefined functions through which the application 1210-1through 1210-n can give instructions to OS 1230 and the user informationcontrol unit 1260.

The user information control unit 1260 controls the user information.The communication control unit 1270 controls the communication withexternal control apparatuses (to be described later) connected with theinformation processing apparatus 1000 through a network.

The user information control unit 1260 determines the informationstorage apparatus in which the user information required by theapplication program 1210-1 through 1210-n is stored and provides theuser information stored in the determined information storage apparatusto the application program 1210-1 through 1210-n.

OS 1230 controls processes created by the execution of the applicationprograms 1210-1 through 1210-n, the user information control unit 1260,and the communication control unit 1270 in parallel. OS 1230 givesinstructions to the hardware resources 1100 through BIOS 1240 and thedevice drivers 1250.

The hardware configuration of the information processing apparatus 1000will be described below. FIG. 2 is a schematic diagram showing thehardware configuration of the information processing apparatus 1000according to an embodiment. The information processing apparatus 1000 isconfigured by an input unit 1510, a display unit 1520, a secondarystorage unit 1530, a memory unit 1540, a processing unit 1550, and acommunication unit 1560 all of which are mutually connected via a bus B.

The input unit 1510 includes input devices such as a keyboard and amouse. An operator can give the information processing apparatus 1000various instructions by operating the input unit 1510. The display unit1520 displays various windows and data for the operator. The secondarystorage unit 1530 stores therein computer programs and various files anddata that are needed for the performance of the computer programs. Thecommunication unit 1560 communicates with an external control apparatusto be described later that is connected through a network.

The memory unit 1540 stores the computer programs retrieved from thesecondary storage unit 1530 when the power of the information processingapparatus is turned on. The processing unit 1550 executes the computerprograms stored in the memory unit 1540.

When the information processing apparatus 1000 is turned on, computerprograms read from the secondary storage apparatus 1530 are stored inthe memory unit 1540. The processing unit 1550 runs the computerprograms stored in the memory unit 1540.

The information processing apparatus 1000 is connected to othercomputers and distributes image information and so forth to the othercomputers. The information processing apparatus 1000 provided with sucha distribution function usually stores the distribution addressinformation and the user restriction/charge information as userinformation. The information processing apparatus 1000 that is notprovided with such a distribution function may store only the userrestriction/charge information.

As an example of the information processing apparatus 1000 according toan embodiment of the present invention, an image forming apparatus 1will be described below. The image forming apparatus is provided withvarious functions such as those of a printer, a copier, a facsimile, anda scanner, and therefore is called a multifunctional apparatus.

FIG. 3 is a schematic diagram showing a multifunctional apparatus 1according to an embodiment of the present invention. The multifunctionalapparatus 1 includes the following: a black & white laser printer 11, acolor laser printer 12, other hardware resources 13, software resources20, and a multifunctional apparatus startup unit 50. The softwareresources 20 further include application programs 30 and a platform 40.

The platform 40 further includes the following: control services 42,44-49 that interpret processing requests from the application programs30 and control one or more hardware resources, a system resource manager(SRM) 43 that controls one or more hardware resources and arbitrates therequests from the control services, and operating system (OS) 41.

The control services include one or more service modules such as asystem control service (SCS) 42, an engine control service (ECS) 44, amemory control service (MCS) 45, an operation panel control service(OCS) 46, a facsimile control service (FCS) 47, a network controlservice (NCS) 48, and a user control service 49.

The platform 40 has an application program interface (API) that canreceive processing requests from the application programs 30 bypredefined functions.

The OS 41 is, for example, UNIX (trade mark). The OS 41 executes thesoftware programs of the platform 40 and the application programs 30 asprocesses in parallel.

The process of SRM 43 controls the system and manages resources togetherwith SCS 42. For example, the process of SRM 43 arbitrates requests froman upper rank layer, to use hardware resources such as engines, thememory unit, files stored in a hard disk drive (HDD), host input/output(I/O) (Centronics interface, network interface, IEEE 1394 interface,RS232C interface, for example), and controls their execution.

In response to a request from the upper rank layer, SRM 43 determineswhether the requested hardware resource is in use and, if not, informsthe upper rank layer that the requested hardware resource is availablefor use. SRM 43 schedules the use of hardware resources based on therequests from the upper rank layer. SRM 43 also directly controls thepaper transportation and the image forming of the printer engine, memoryreservation, and file generation.

The process of SCS 42 performs application administration, operationalunit control, system screen display, LED display, resourceadministration, interruption application control, and so forth.

The process of ECS 44 controls the engines of the black & white laserprinter 11, the color laser printer 12, and the hardware resource 13.

The process of MCS 45 reserves and discharges image memory, controls thehard disk drive (HDD), and compresses and decompresses the image data.

The process of OCS 46 controls the operation panel that helps themultifunctional apparatus 1 to communicate with the operator.

The process of FCS 47, in response to a request from the applicationlayer of the system controller, transmits and receives facsimile throughPSTN or ISDN, for example, registers and retrieves various facsimiledata stored in the backup SRAM (BKM), reads documents, prints receivedfacsimile, and performs multifunctional communication.

The process of NCS 48 provides common services to applications thatrequire communication through a network. The process of NCS 48distributes data received from the network to corresponding applicationsprograms and intermediates the transmission of data from an applicationprogram to the network.

The process of UCS 49 controls the user information by determining theinformation storage apparatus storing the requested user information andproviding the user information from the determined information storageapparatus to the application programs.

The application programs 30 provides users with various user servicessuch as those of a printer, a copier, a facsimile, and a scanner. Theapplication programs 30 includes the following: a printer application 31that causes the multifunctional apparatus 1 to function as a printersupporting page description languages (PDL, PCL) and postscript (PS),for example, a copier application 32, a facsimile application 33, ascanner application 34, a network file application 35, and in-lineinspection application 36.

The multifunctional apparatus startup unit 50 performes at first whenthe multifunctional apparatus 1 is turned on and activates theapplication programs 30 and the platform 40. For example, themultifunctional apparatus startup unit 50 reads the control services andthe application programs from a flash memory (to be described later) andtransfers them to a memory region reserved in SRAM or SDRAM, forexample, for execution.

FIG. 4 is a schematic diagram showing the hardware configuration of amultifunctional apparatus according to an embodiment. Themultifunctional apparatus 1 of FIG. 4 is provided with the following: acontrol board 60, an operation panel 70, a facsimile control unit (FCU)80, a USB interface 90, an IEEE 1394 interface 100, and an engine unit110. FCU 80 includes another memory unit that temporarily storesfacsimile data received while the multifunctional apparatus 1 is turnedoff.

The operation panel 70 is directly connected to ASIC 66 of the controlboard 60. FCU 80, USB interface 90, IEEE1394 interface 100, and theengine unit 110 are connected to ASIC 62 of the control board 60 througha PCI bus and so forth.

The control board 60 is further provided with a CPU 61, a static RAM(SRAM) 63, a Synchronous DRAM (SDRAM) 64, a flash memory 65, an HDD 66,a network interface controller 67 that are connected to the ASIC 62.

CPU 61 controls the entire system of the multifunctional apparatus 1.CPU 61 and ASIC 66 are connected each other through NB that is a CPUchip set. As described above, even if the information of the interfaceof CPU 61 is not available, ASIC 66 can be connected to CPU 61 throughNB.

CPU 61 controls the entire operation of the functional apparatus 1. CPU61 executes processes of SCS 42, SRM 43, ECS 44, MCS 45, OCS 46, FCS 47,and NCS 48 that are included in the platform 40 under the control of theOS 41. CPU 61 further runs the printer application 31, the copierapplication 32 the facsimile application 33, the scanner application 34,the net file application 35, and the in-line inspection application 36that are included in the application 30.

ASIC 62 is an integrated circuit of which hardware is designed for imageprocessing. The virtual memory spaces of the kernel and the processes ofthe application programs are mapped over the physical memory spaceprovided by the SRAM 63 and the SDRAM 64.

The flash memory 65 is a non-volatile random access memory that storestherein the application programs of the application 30, the controlservices of the platform 40, computer programs such as SRM 43, and theuser restriction/charge information.

HDD 66 is a storage device that stores therein image data, computerprograms, font data, form data, and the distribution addressinformation.

The operation panel 70 is an input device with which the operator canoperate the multifunctional apparatus 1, and at the same time, is adisplay device through which the system displays information to theoperator.

The multifunctional apparatus 1 may be connected to anothermultifunctional apparatus, a computer, and so forth through a networkand thereby distribute image data and so forth. The multifunctionalapparatus 1 with such a distribution function stores therein the userinformation such as the distribution address information and the userrestriction/charge information. The multifunctional apparatus 1 withoutsuch a distribution function may store only the user restriction/chargeinformation therein.

The method of controlling user information according to the presentinvention will be described using the multifunctional apparatus 1 as anexample of the information processing apparatus 1000 according to thepresent invention.

First Embodiment

FIG. 5 is a schematic diagram for explaining the method of controllinguser information according to an embodiment of the present invention.The user restriction/charge information stored in the flash memory 65 isused for controlling the authorization of various functions as entitledto each user and the quantity of authorized function consumed by eachuser. For example, the user restriction/charge information is configuredas showed in FIG. 6.

FIG. 6 is a table showing the user restriction/charge information. Theuser restriction/charge information showed in FIG. 6 includes data itemssuch as Identification No., Registration No., user name, user code,authorization (user restriction) for the copying function, the number ofcopied pages, authorization (user restriction) for distributing, and thenumber of distributed pages. The user restriction/charge informationstored in the flash memory 65 is controlled by the charge informationcontrolling module 121 included in the SCS 42.

The parameters of various services, modules, and application programsare also stored in the flash memory 65 and are controlled by the systeminitializing module (not showed) included in the SCS 42.

The distribution address information stored in the HDD 66 is used tocontrol the addressees and the senders of distribution information andis configured as showed in FIG. 7. FIG. 7 is a table showing thedistribution address information, for example. The distribution addressinformation of FIG. 7 includes data items such as identification No.,registration No., user name, e-mail address, and the authorization (userrestriction) for sending. The distribution address information stored inthe HDD 66 is controlled by the USC 49.

The UCS 49 directly controls the distribution address information storedin the HDD 66 and, at the same time, indirectly controls the userrestriction/charge information stored in the flash memory 65 through thecharge information controlling module 121.

In the case of the multifunctional apparatus 1 without the distributionfunction, no distribution address information is stored in the HDD 66.Even in this case, the multifunctional apparatus 1 can have the sameinterface as that of the multifunctional apparatus 1 with thedistribution function because the UCS 49 can indirectly control the userrestriction/charge information stored in the flash memory 65 through thecharge information controlling module 121.

The multifunctional apparatus showed in FIG. 5, stores the userrestriction/charge information in the flash memory 65 and thedistribution address information in the HDD 66. The userrestriction/charge information, the distribution address information, orboth may be stored in the memory unit included in the FCU 80.Alternatively, the portion of the user restriction/charge information orthe portion of the distribution address information may be stored in thememory unit included in the FCU 80.

The case where the facsimile application 33, as an example of theapplication programs 30, accesses the user information through the UCS49 will be described by reference to the drawings.

FIG. 8 is a schematic diagram for explaining the access of the facsimileapplication 33 to the user information. The facsimile application 33, asa client of the UCS 49, requests for access to the user informationthrough the API provided by the UCS 49.

The UCS 49 determines in which, the flash memory 65 or the HDD 66, theuser information requested by the facsimile application 33 is stored.Then, the UCS 49 obtains the requested user information from either theflash memory 65 or the HDD 66, and provides the obtained userinformation to the facsimile application 33.

In particular, when the facsimile application 33 request for access tothe distribution address information, the UCS 49 obtains a requesteditem of the distribution address information from the HDD 66 andprovides the obtained item to the facsimile application 33. When thefacsimile application 33 requests for access to the userrestriction/charge information, the UCS 49 obtains the requested item ofthe user restriction/charge information from the flash memory 65 throughthe charge information controlling module 121 and provides the obtaineditem to the facsimile application 33.

Accordingly, the facsimile apparatus 33 can obtain a desired item of theuser information from the UCS 49 without designating where the desireditem of the user information is stored. The initializing process to beperformed by the facsimile application 33 will be described below.

The UCS 49, as a server, creates a thread and opens a socket to wait fora request. The facsimile application 33, as a client, creates a threadand opens a socket to wait for an event. The facsimile application 33registers its subscription through the socket that the UCS 49 opens.

The inter-process communication between the request from the facsimileapplication 33 received through the socket of the UCS 49 and the eventfrom the UCS 49 received through the socket of the facsimile application33 enables the facsimile application 33 and the UCS 49 to operate incollaboration with each other.

The operation in which the scanner application 34 displays thedistribution address information on the operation panel 70 will bedescribed as an example by reference to the drawings. FIG. 9 is a flowchart showing the operation in which an application program accesses thedistribution address information.

The scanner application 34 obtains configuration information from UCS 49using the API (step S110). The configuration information is informationabout the configuration of the UCS 49. The configuration informationcontains information about incorporation and parameters of the UCS 49and the charge information controlling module 121. This step S110 willbe described in more detail later.

Subsequently to the step S110, the scanner application 34 determinesusable functions from the obtained configuration information andregisters the functions to be used using the API at the UCS 49 (stepS111). After this registration in the UCS 49, of the functions to beused, the scanner application 34 is automatically notified of theupdates of the user information.

For example, if e-mail address information is usable, the scannerapplication 34 registers the e-mail address information as a function tobe used, in the UCS 49. Subsequently, when the e-mail addressinformation is updated, the UCS 49 informs the scanner application 34 ofthe update. The step S111 will be described in more detail later.

Next to the step S111, the scanner application 34 obtains tag setinformation and tag information from the UCS 49 through the API (stepS112).

FIG. 10 illustrates a tag set and tags. A tag set 122 and tags 123 areadditional information for better user interface. The tag set 122 is anordered set of tags such as “Frequently Used”, “ABC”, and so forth, andcontains the information of tags attached to the tag set. The tag 123 isa labeled ordered set of entries and contains the information of thelabel and entries attached thereto.

In addition, the “Frequently Used” tag 123 is a special tag that isattached to all tag sets. Tags 123 other than the “Frequently Used” arenot attached to a plurality of tag sets. A more detailed description onthis step will be given later.

Subsequent to the step S112, the scanner application 34 obtains theentries attached to a selected tag from the UCS 49 using the API (stepS113).

FIG. 11 is a schematic diagram illustrating entries. One or more entries125 constituting the entries 124 are divided into accounts correspondingto individual users and groups corresponding to enumerated accounts.This step S113 will be described in more detail later.

Next after step S113, the scanner application 34 creates an entryselection screen as showed in FIG. 12 and displays the entry selectionscreen on the operation panel 70 (step S114). FIG. 12 is a schematicdiagram illustrating the entry selection screen.

The entry selection screen of FIG. 12 is created based on the tag set,the tags, and the entries. An icon in which a small image of threepeople is showed at the upper right corner indicates a group ofaccounts. An icon without the small image of three people at the upperright corner indicates an individual account.

Next after step S114, the scanner application 34 determines whether anentry is selected from the entry selection screen (step S115). If thescanner application 34 determines that an entry is already selected (YESbranch of S115), the scanner application 34 performs step S116. If thescanner application 34 determines that no entry is selected yet (NObranch of S115), the scanner application 34 performs step S117.

The scanner application 34 obtains the detailed information of theselected entry from the UCS 49 using the API (step S116), and thenperforms step S117. For example, the scanner application 34 may displaythe obtained detailed information of the selected entry in theinformation display field of the entry selection screen of FIG. 12.

The scanner application 34 determines whether another tag is selectedfrom the entry selection screen (step S117). If the scanner application34 determines that another tag is selected (YES branch of S117), thescanner application 34 returns to previous step S113. If the scannerapplication 34 determines that no tag is selected (NO branch of S117),the scanner application performs step S118.

The scanner application 34 determines whether it is informed by the UCS49 of any update in the user information (step S118). If the scannerapplication 34 determines that it receives the update information (YESbranch of S118), the scanner application 34 returns to previous stepS112. If the scanner application 34 determines that it has not receivedthe update information (NO branch of S118), the scanner application 34returns to previous step S115.

Furthermore, the steps of the flow chart showed in FIG. 9 will bedescribed in more detail by reference to the drawings. FIG. 13 is a flowchart illustrating the step S110 of obtaining the configurationinformation. The scanner application 34 requests the UCS 49 to give theconfiguration information using the API for obtaining the configurationinformation (step S121). FIG. 14 illustrates the API for obtaining theconfiguration information.

After step S121, the UCS 49 provides the scanner application 34 with theconfiguration information (step S122). The UCS 49 creates theconfiguration information based on the incorporation information, theparameters, hardware configuration information, and charge informationconfiguration obtained from the charge information controlling module121. The charge information controlling module 121 sets up the chargeinformation configuration based on the incorporation information, theparameters, and the hardware configuration information.

The configuration information of FIG. 15 contains a service version,usable functions, and the maximum number of entries to be registered.The service version is incorporation information of the UCS 49. Theusable functions are determined by the UCS 49 based on the hardwareconfiguration information, and indicates the existence of the chargeinformation and the e-mail address information. The maximum number ofentries to be registered is a control parameter of the UCS 49 indicatingthe maximum number of entries that the UCS 49 can register. An entry isthe minimum unit containing the distribution address, the sender, achargeable user and so forth and further contains a name and ID number.

The step S111 for registering functions to be used will be described inmore detail. FIG. 16 is a flow chart showing the step S111 forregistering functions to be used. The scanner application 34 determinesusable functions based on the configuration information obtained in stepS122 (step S131).

Subsequent to step S131, the scanner application 34 selects functions tobe used from the usable functions determined in step S131 (step S132).After step S132, the scanner application 34 request the UCS 49 toregister the functions selected in step S132 using the API forregistering functions to be used (step S133). FIG. 17 illustrates theAPI for registering functions to be used.

After step S133, the UCS 49 stores the corresponding relationshipbetween the scanner application 34 that requests for the registrationand the registered functions (step S134). After this step S134, when theuser information is updated, the UCS 49 informs the scanner application34 of the update.

Accordingly, since the scanner application 34 is informed of the updatein the user information, the scanner application 34 can re-obtain theupdated user information.

A description about step S112 for obtaining a tag set and a tag will begiven next. FIG. 18 is a flow chart illustrating step S112 for obtaininga tag set and a tag.

The scanner application 34 requests for all tag sets of the UCS 49 usingthe API for obtaining a tag set (step S41). FIG. 19 illustrates an APIfor obtaining a tag set.

Subsequent to step S141, the UCS 49 provides all tag sets to the scannerapplication 34 (step S142). FIG. 20 illustrates a tag set. The tag setof FIG. 20 contains data items such as an ID number, the number of tagsattached to the tag set, and attached tags. The ID numbers of tagsattached to the tag set are stored in the attached tags field.

After step S142, the scanner application 34 selects tag sets and tagsbased on the reference value of the tag sets and the tags that thescanner application 34 contains as the control parameters (step S143).

Subsequent to step S143, the scanner application 34 requests for alltags attached to the tag sets selected in step S143, from the UCS 49using an API for obtaining tags (step S144). FIG. 21 illustrates the APIfor obtaining tags.

Subsequent to step S144, the UCS 49 reads tags from the HDD 66 andprovides the tags to the scanner application 34. FIG. 22 illustrates taginformation. The tag information of FIG. 22 contains data items such asa tag ID number, a tag category, and a label. The tag category is usedto identify whether the tag is “frequently used” or not.

The next step S113 for obtaining tag entries will be described below.FIG. 23 is a flow chart showing step S113 for obtaining tag entries.

The scanner application 34 requests the tag entries attached to the tagselected in step S143 from the UCS 49 using an API for obtaining tagentries (step S151). FIG. 24 illustrates the API for obtaining tagentries.

After step S151, the UCS 49 reads the tag entries from the HDD 66 andprovides the read tag entries to the scanner application 34 (step S152).FIG. 25 illustrates the tag entries. The tag entries of FIG. 25 containdata items such as an entry ID number, an entry index number, an entrycategory, and a user name. The entry index number is attached so thatusers can easily memorize it. The entry category indicates whether auser is authorized to become an addressee of distribution, whether theuser is authorized to become a sender, and whether the entry is anaccount or a group of accounts.

It is not necessary to obtain all the tag entries attached to the tag atonce. Only tag entries that fit a screen of the operation panel 70 maybe obtained at first. The tag entries may be filtered by designatingfiltering conditions so that only entries having e-mail addresses orbeing authorized to become senders, for example, are displayed.

The case in which an entry index number is input to a direct input field126 in the entry selection screen of FIG. 12 will be described. FIG. 26is a flow chart showing a step for processing an input of an entry indexnumber.

Using an API for obtaining an entry control number corresponding to anentry index number, the scanner application 34 obtains from the UCS 49an entry control number corresponding to the entry index number input inthe direct input field 126 (step S161). FIG. 27 illustrates the API forobtaining an entry control number corresponding to an entry indexnumber.

Subsequent to step S161, the scanner application 34, using an API forobtaining a tag to which an entry is attached based on the entry controlnumber of the entry, obtains from the UCS 49 the tags to which the entryis attached based on the entry control number obtained in step S161(step S162). FIG. 28 illustrates the API for obtaining tags to which anentry is attached from its entry control number.

Then, the scanner application 34 determines whether the tags obtained instep S162 is included in the currently selected tag set (step S163).

If the tags obtained in step S162 are included in the currently selectedtag set (YES branch of S163), the scanner application 34 selects one tagincluded in the currently selected tag set out of the tags obtained instep S162 (step S164). If more than one tags obtained in step S162 areincluded in the currently selected tag set, one of the tags needs to beselected in compliance with appropriate criteria such as the order oftheir tag control numbers, for example.

On the other hand, if none of the tags obtained in step S162 is includedin the currently selected tag set (NO branch of S163), the scannerapplication 34 select one tag set and one tag in compliance withappropriate criteria (step S165).

After step S164 or step S165, the scanner application 34 obtains fromthe UCS 49 tag entries attached to the tag selected in step S164 or stepS165 using the API for obtaining tag entries (step S166). Then, thescanner application 34 creates, using the obtained tag entries, theentry selection screen as showed in FIG. 12 and displays it on theoperation panel 70.

If the order of tag entries is known, the step S166 may be easy. In thecase where 12 tag entries can be displayed in one screen of theoperation panel 70 and the order of a desired entry is the 20^(th), forexample, only 12 entries starting with the 13^(th) entry may beobtained.

Using an API for obtaining the order of entries, the scanner application34 obtains the order of entries attached to a tag from the UCS 49. FIG.29 illustrates the API for obtaining the order of entries.

Thanks to this API for obtaining the order of entries, it is notnecessary to repeat a step for obtaining 12 entries and determiningwhether the desired entry is included in the obtained entries.

The UCS 49 provides an API for obtaining mail information as well. FIG.30 illustrates the API for obtaining the e-mail information. The scannerapplication 34 can obtain the mail information such as e-mail addressesfrom the UCS 49 using the API for obtaining mail information.

FIG. 31 illustrates an API for obtaining sender authenticationinformation. The scanner application 34 obtains the senderauthentication information from the UCS 49 using the API for obtainingthe sender authentication information. The sender authenticationinformation is a password, for example, that is used to identify thesender.

FIG. 32 illustrates an API for obtaining user restriction information.The scanner application 34 obtains the user restriction informationusing the UCS 49. The user restriction information is a series of flagsindicating specific restrictions such that the user is prohibited fromusing the color LP, or that the user is prohibited from using the black& white LP, for example.

FIG. 33 illustrates an API for obtaining e-mail group information. Thescanner application 34 obtains e-mail group information from the UCS 49using the API for obtaining e-mail group information. The e-mail groupinformation is information such as the number of accounts attached to ane-mail group and the accounts themselves attached to the e-mail group.

FIG. 34 illustrates an API for searching entries. The scannerapplication 34 causes the UCS 49 to search entries using this API forsearching entries. Various search conditions such as forward match,backward match, and partial match.

In the above description by reference to FIG. 8, the facsimileapplication 33 creates the screen to be displayed on the operation panel70. Another separate module for creating a screen to be displayed on theoperation panel 70 may be provided.

FIG. 35 is a schematic diagram showing the operation of a module forcreating a screen. The screen creating module 130 included in the SCS 42creates a screen to be displayed on the operation panel 70 in responseto a request from the facsimile application 33 and the scannerapplication 34.

As described above, the facsimile application 33 and the scannerapplication 34 can share the screen creating module 130 that is providedseparately.

Since the multifunctional apparatus 1 is provided with the UCS 49, aplurality of applications programs such as the facsimile application 33and the scanner application 34 can share the user information.Whichever, the flash memory 65 or the HDD 66, the user information isstored in, the application programs can obtain the user information byaccessing only the UCS 49.

In FIG. 1, the UCS 49 is included in the control service, but the UCS 49may be included in the application program 30, for example. In addition,in FIG. 8, the facsimile application 33 and the scanner application 34access the user information through the API provided by the UCS 49, butthe control service may access the user information through the APIprovided by the UCS 49, for example.

Though the multifunctional apparatus 1 is mainly described in thisembodiment, those skilled in the art may easily recognize that thepresent invention is also applicable to the information processingapparatus 1000 showed in FIGS. 1 and 2. In the case of the informationprocessing apparatus 1000, the user information processing unit 1260,instead of the UCS 49 of FIGS. 5 and 8, controls the user information.In this case, no unit corresponding to the SCS 42 is required.

Second Embodiment

A detailed description of the information processing apparatus accordingto the second embodiment of the present invention will be given below.The hardware configuration of the information processing apparatus isidentical to that of the information processing apparatus according tothe first embodiment. The software configuration thereof is alsosubstantially identical to the first embodiment. Accordingly, only whatis different will be mainly described.

The updating of the user information by the system initialization module122 included in the SCS 42 using the UCS 49 will be described below.

FIG. 36 is a schematic diagram for explaining the updating operation ofthe user information. The system initializing module 122 as a clientrequests the UCS 49 to update the user information.

The UCS 49 determines which, the flash memory 65 or the HDD 66, the userinformation requested by the system initialization module 122 is storedin. The UCS 49 updates the user information stored in the flash memory65 or the HDD 66 in response to the request from the systeminitialization module 122 for updating.

In particular, the UCS 49 updates the distribution address informationstored in the HDD 66 in response to the request from the systeminitialization module 122 for updating the distribution addressinformation. The UCS 49 also updates the user restriction/chargeinformation stored in the flash memory 65 in response to the requestfrom the system initialization module 122 for updating the userrestriction/charge information. The UCS 49 updates the userrestriction/charge information stored in the flash memory 65 via thecharge information controlling module 121.

Accordingly, the system initialization module 122 can update the userinformation without designating where the user information desired to beupdated is stored. The system initialization module 122 initiates theuse of the UCS 49 as follows.

The UCS 49 as a server creates a thread for waiting for a request, opensa socket, and waits for the request. The system initialization module122 creates a thread to wait for an event, opens a socket, and waits forthe event. At the same time, the UCS 49 registers a subscription throughthe socket.

The inter-process communication between the request from the systeminitialization module 122 and the event from the UCS 49 through thesocket of UCS 49 and the socket of the system initialization module 122,respectively, enables the system initialization module 122 and the UCS49 to collaborate.

Next, the operation of the system initialization module 122 to updatethe user information will be described by reference to another drawing.FIG. 37 is a flow chart showing the updating operation of thedistribution address information.

The system initialization module 122 obtains the configurationinformation of the UCS 49 using an API (step S210). The configurationinformation is information about the configuration of the UCS 49, andincludes the incorporation information and the setup parameterinformation of the UCS 49 and the charge information controlling module121.

Next to step S210, the system initialization module 122 determinesusable functions based on the obtained configuration information andregisters the functions to be used in the UCS 49 using an API (stepS211).

Subsequent to step S211, the system initialization module 122 creates amenu screen for system initialization and displays the menu screen onthe operation panel 70 (step S212). FIG. 38 is a schematic diagram ofthe menu screen for the system initialization.

The menu screen for system initialization of FIG. 38 includes one ormore menu buttons 2130 corresponding to processing to update the userinformation. A user can select a desired operation by pressing a menubutton 2130 displayed in the menu screen for system initialization onthe operation panel 70.

After step S212, the system initialization module 122 determines whethera menu item has been selected (step S213). If the system initializationmodule 122 determines that a menu item has been selected from the systeminitialization menu screen (YES branch of S213), the systeminitialization module 122 processes the selected menu item (step S214).A detailed description on step S214 will be given later.

On the other hand, if the system initialization module 122 determinesthat no menu item has been selected from the system initialization menuyet (NO branch of S213), the system initialization module 122 repeatsstep S213.

Step S214 will be described in detail by reference to the drawingsbelow. If an item “USER (ADDRESS) REGISTRATION/UPDATE/DELETION” isselected from the system initialization menu, the system initializationmodule 122 displays an entry information updating screen as showed inFIG. 39 on the operation panel 70. The system initialization module 122obtains information that is needed to create the entry informationupdating screen such as tag set information, tag information, and tagentries attached to a tag from the UCS 49 using an API.

FIG. 39 is a schematic diagram of the entry information updating screen.An entry means a user (address) and is divided into an accountcorresponding to an individual user and a group of accounts.

The entry information update screen of FIG. 39 includes a tag set 2132including one or more tags, an entry display field 2134 displaying tagentries attached to the selected tag, a new item button 2136 with whichthe user can open a new screen to create and register new entryinformation, an update button 2138 for updating an entry informationthat is already registered, and a deletion button 2140 for deleting aselected entry information.

The tag set 2132 is an ordered set of tags such as “FREQUENTLY USED” and“AB”. The tag is a labeled ordered set of entries. In the entryinformation updating screen of FIG. 39, a tag “AB” is selected, and 7entries attached to the tag “AB” are displayed in an entry display field2134.

If the new entry button 2136 is selected, the system initializationmodule 122 displays an entry information registration screen as showedin FIG. 40 on the operation panel 70 so that the user can create a newentry and register it. FIG. 40 is a schematic diagram showing the entryinformation registration screen.

The entry information registration screen of FIG. 40 includes a field toinput user name (address), a field to input the index number, tagbuttons to set a tag to which the entry is attached, a user code button2142 to enter a screen for inputting a user code, a mail address button2144 to enter a screen for inputting a mail address, a facsimile numberbutton 2146 to enter a screen for inputting a facsimile number, a groupbutton 2148 to enter a screen for setting a group, and a registrationbutton 2150 to register the entry information.

A user sets a user (address) name, an index number, and a tag to whichthe user is attached in the entry information registration screen. Theuser inputs the user code in the displayed screen for setting the usercode by selecting the user code button 2142. The user code isinformation indicating the restrictions on functions that the user canuse.

The user can input the mail address by selecting the mail address button2144 and displaying a screen for setting the mail address on theoperation panel 70. The user further can input the facsimile address byselecting the facsimile number button 2146 and displaying a screen forinputting the facsimile number on the operation panel 70. Furthermore,the user can select a group to which the entry is to be attached byselecting the group button 2148 and displaying a screen for setting agroup on the operation panel 70.

After setting all information that is required for an entry, the userselects the registration (enter) button 2150 of the entry informationregistration screen of FIG. 40. The system initialization module 122requests the UCS 49 to update the entry information using various APIs.

The system initialization module 122 requests the UCS 49 to create theentry using an API showed in FIG. 41. FIG. 41 illustrates an API forcreating an entry. The UCS 49 creates an entry in response to this API.When a new entry is created, the new entry is displayed in the entrydisplay field 2134 of the entry information updating screen, forexample.

The system initialization module 122 also requests the UCS 49 to set anentry tag to which the entry is to be attached using an API as showed inFIG. 42. FIG. 42 illustrates the API for setting entry tag to which anentry is to be attached. The UCS 49 sets the entry tag in response tothe API for setting the entry tag to which the entry is to be attached.

Using an API showed in FIG. 43, the system initialization module 122request the UCS 49 to set a usercode. FIG. 43 illustrates an API forsetting the usercode. The UCS 49 sets the usercode in compliance withthe API.

Using an API as showed in FIG. 44, the system initialization module 122requests the UCS 49 to set a mail address. FIG. 16 illustrates the APIfor setting the mail address. The UCS 49 sets the mail address incompliance with the API for setting the mail address.

Using an API, the system initialization module 122 requests the UCS 49to set a facsimile number (destination). The UCS 49 sets the facsimilenumber (destination) in compliance with the API.

The system initialization module 122, using an API as showed in FIG. 45,determines whether the index number set in the entry informationregistration screen is already registered. If the index number isalready registered, the system initialization module 122 requests theUCS 49 to obtain an unused index number close to the already registeredindex number.

FIG. 45 illustrates an API for obtaining an index number. Using an APIfor checking index number, the UCS 49 determines whether the indexnumber set in the entry information registration screen is alreadyregistered. If the index number is already registered, the UCS 49obtains an unused index number near the already registered index number.

When the update button 2138 in the entry information updating screen ofFIG. 39 is selected, the system initialization module 122 displays theentry information registration screen for updating already registeredentry information as showed in FIG. 40 on the operation panel 70. Theentry information registration screen showed when the update button 2138is selected is different from the entry information registration screenshowed when the new entry button 2136 is selected in that alreadyregistered entry information is displayed.

Using various APIs, the system initialization module 122 displaysalready registered entry information in the entry informationregistration screen. The system initialization module 122 obtains agroup to which an entry is attached from the UCS 49 using an API showedin FIG. 46. FIG. 46 illustrates an API for obtaining a group to which anentry is attached.

The description of the registration of information in the entryinformation registration screen will be omitted since the registrationof information in the entry information registration screen displayedwhen the update button 2138 is selected is the same as that in the entryinformation registration screen displayed when the new entry button 2136is selected.

After inputting all information needed to update the entry information,the user selects the enter button 2150. In response to the selection,the system initialization module 122 requests the UCS 49 to update theentry information using various APIs.

For example, the system initialization module 122 uses an API as showedin FIG. 47 to request the UCS 49 to update the entry. FIG. 47illustrates the API for updating the entry. The UCS 49 updates the entryin compliance with the API.

On the other hand, when an entry in the entry display field 2134 of theentry information updating screen of FIG. 39 is selected and then, thedelete button 2140 is selected, the system initialization module 122deletes the entry using an API of FIG. 48. FIG. 48 illustrates the APIfor deleting an entry.

When the “editing tags” is selected in the system initialization menu ofFIG. 38, the system operates as follows. When the “editing tags” isselected, the system initialization module 122 displays a tag editingscreen on the operation panel 70. The tag editing screen includes thetag sets 2132 identical to that of the entry information updating screenof FIG. 39. Using an API, the system initialization module 122 obtainstag set information and tag information that are needed to create thetag editing screen from the UCS 49.

After inputting all information required to update tags, the userselects the enter button of the tag editing screen, for example. Inresponse to the selection, the system initialization module 122 requeststhe UCS 49 to update the tags using an API as showed in FIG. 49. FIG. 49illustrates an API for updating the tags. The UCS 49 updates the tags incompliance with the API.

When “changing entry order” is selected in the system initializationmenu screen, the system operates as follows. When “changing entry order”is selected, the system initialization module 122 displays an entryorder change screen on the operation panel 70. The entry order changescreen includes, as the entry information updating screen does, a tagset 2132 and an entry display field 2134 in which entries attached tothe selected tag are displayed. The system initialization module 122obtains the tag set information and tag information that are requiredfor creating the entry order change screen from the UCS 49 using an API.

The user changes the order of entries displayed in the entry displayfield 2134, for example, as desired and selects the enter button of theentry order change screen, for example. The system initialization module122 requests the UCS 49 to change the order of entries using an API asshowed in FIG. 50. FIG. 50 illustrates an API for changing the order ofentries. The UCS 49 changes the order of entries in compliance with theAPI.

The UCS 49 can support the following API. FIG. 51 illustrates an API forsetting sender authentication. The system initialization module 122requests the UCS 49 to set the sender authentication information usingthe API for setting sender authentication. The sender authenticationinformation is a password, for example, that can be used to identify asender.

FIG. 52 illustrates an API for setting a mail group. The systeminitialization module 122 requests the UCS 49 to set a mail group usingthe API for setting a mail group. The mail group means information suchas the number of accounts and the accounts attached to the mail group.

FIG. 53 illustrates the API for obtaining the number of entriesregistered. The system initialization module 122 can obtain the numberof registered entries from the UCS 49 using the API for obtaining thenumber of entries registered.

FIG. 54 illustrates an API for obtaining the number of accountsregistered. The system initialization module 122 can obtain the numberof registered entries from the UCS 49 using the API for obtaining thenumber of registered accounts.

FIG. 55 illustrates an API for obtaining the number of registeredgroups. The system initialization module 122 can obtain the number ofregistered groups from the UCS 49 using the API for obtaining the numberof registered groups.

FIG. 56 illustrates an API for obtaining the number of registered mailaddresses. The system initialization module 122 can obtain the number ofregistered mail addresses from the UCS 49 using the API for obtainingthe number of registered mail addresses.

FIG. 57 illustrates an API for obtaining the number of registeredusercodes. The system initialization module 122 can obtain the number ofregistered usercodes from the UCS 49 using the API for obtaining thenumber of registered usercodes.

The numbers of entries, accounts, groups, mail addresses, and usercodesare used to create a screen to update the information of the entries,the accounts, the groups, the mail addresses, and the usercodes, forexample.

As described above, since the UCS 49 that controls the user informationis provided, the system initialization module 122 can update the userinformation without designation of where the user information is stored.

In FIG. 3, the UCS 49 is included in the control service, but the UCS 49may be included in the application program 30, for example. In addition,in FIG. 36 and so forth, the system initialization module 122 requeststhe UCS 49 to update the user information using the API provided by theUCS 49, but the present invention is not limited to this example. Theapplication programs 30 such as the facsimile application 33 may requestthe UCS 49 to update the user information using the API provided by theUCS 49, for example.

Though the multifunctional apparatus 1 is mainly described in thisembodiment, those skilled in the art may easily recognize that thepresent invention is also applicable to the information processingapparatus 1000 showed in FIGS. 1 and 2. In the case of the informationprocessing apparatus 1000, the user information processing unit 1260,instead of the UCS 49 of FIGS. 5 and 8, controls the user information.In this case, no unit corresponding to the SCS 42 is required.

Third Embodiment

The method of controlling the user information according to the thirdembodiment of the will be described below. The multifunctional apparatus1 will be mainly described as an example of the information processingapparatus 1000 according to the present invention.

FIG. 58 is a schematic diagram for explaining the method of controllingthe user information according to this embodiment. FIG. 58 shows theconfiguration of the multifunctional apparatus 1 according to thisembodiment. The components that are identical to those showed in FIG. 5are referred to by the same reference numerals, and their description isomitted.

A remote interface 125 in the UCS 49 and an external control apparatus124 communicates through the NCS 48 and the network 123 using the simpleobject access protocol (SOAP) for exchanging messages expressed in theextensible markup language (XML).

The remote interface 125 has one or more web service functions (WSF) forrealizing web services. The external control apparatus 124 remotelycontrols the user information by remotely accessing the WSF externallyprovided by the remote interface 125 using SOAP.

FIG. 59 is a schematic diagram for explaining the remote control of theuser information. The external control apparatus 124 has a PROXY 130that translates a web service request (WS request) into XML and outputsthe WS request expressed in XML. The remote interface 122 has an XMLparser 131, a conversion library 132, and one or more WSFs 133 a-133 n.

The XML purser 131 determines whether the WS request follows thedocuments type definition (DTD), analyzes the syntax of the DTD, andconverts the WS request into a tree-shaped parse that the conversionlibrary 132 can use. The conversion library 132 converts the parseprovided by XML parser 131 into WS requests. The WSF 133 a-133 n arefunctions provided by the method of the UCS 49 that realized the webservice.

The PROXY 130 of the external control apparatus 124 converts the WSrequest into XML, and transmits the WS request expressed in XML to theNCS 48 of the multifunctional apparatus 1. The NCS 48 distributes the WSrequest expressed in the XML to XML parser 131 in compliance with theuniform resource locator (URL).

The XML parser 131 converts the WS request expressed in XML to atree-shaped parse that the conversion library 132 can use, and then,provides the WS request to the conversion library 132. The conversionlibrary 132 converts the parse provided by the XML parser 131 into theWS request and identifies the WSF 133 a, for example, corresponding tothe converted WS request. The UCS 49 provides the external controlapparatus 124 with the web service such as the access to or the updatingof the user information.

The PROXY 130, the conversion library 132, and the WSF 133 a-133 n areconstructed based on the web service interface specification as showedin FIGS. 60A-60C described in the web service description language(WSDL). FIGS. 60A-60C show the interface specification written in theWSDL. FIGS. 60A-60C describes the web service to obtain a generationnumber.

A descriptive portion 3140 of the specification indicates that the inputparameter used to obtain the generation number is “ticket” and the datatype is binary. A descriptive portion 3141 of the specificationindicates that the output parameter used to obtain the generation numberis “returnValue” and “generation_out”, the data type of “returnValue” isenumeration, and the data type of “generation_out” is non-negativeinteger.

A descriptive portion 3142 indicates which parameter the methodcorresponding to the obtaining of the generation number uses. Inaddition, <operation name=“getGeneration”> of the descriptive portion142 corresponds to WSF 133 a, for example.

Next, the access to the user information using the remote control willbe described below by reference to the drawings. FIG. 61 is a flow chartshowing the access to the user information using the remote control.

The external control apparatus 124 remote accesses the method providedby the remote interface 125 and uses the web service for obtaining theconfiguration information. Input/output parameters as showed in FIG. 62are used for the web service for obtaining the configurationinformation. FIG. 62 illustrates the input/output parameters used forthe web service for obtaining the configuration information. FIG. 63illustrates the configuration information.

Subsequent to step S310, the external control apparatus 124 remotelyaccesses the method provided by the remote interface 122, and uses a webservice for authenticating a user or an administrator (step S311). Theweb service for authenticating a user or an administrator usesinput/output parameters as showed in FIG. 64. FIG. 64 illustrates theinput/output parameters used for the web service for authenticating auser or an administrator.

The web service receives a password from the external control apparatus124 as an input, and outputs authentication information to the externalcontrol apparatus 124. The authentication information indicates that theuser or the administrator is authenticated. The web service foraccessing and updating the user information requires the authenticationinformation as an input parameter. This requirement prohibitsunauthenticated person from accessing the user information.

After step S311, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125, and uses a web servicefor obtaining generation number (step S312). The web service forobtaining the generation number uses the input/output parameters asshowed in FIG. 64.

FIG. 65 illustrates the input/output parameters used in the web servicefor obtaining the generation number. The web service for obtaining thegeneration number receives the authentication information from theexternal control apparatus 124 as an input parameter and output thegeneration number to the external control apparatus 124 as an outputparameter. Because the generation number is updated whenever the userinformation is updated, the generation number can be used to determinewhether the user information is updated or not in compliance with arequest from another external control apparatus 124.

Subsequent to step S312, the external control apparatus 124 remoteaccesses the method provided by the remote interface 125, and uses a webservice for obtaining the tag set (step S313). Input/output parametersas showed in FIG. 66 are used in the web service for obtaining the tagset. FIG. 66 illustrates the input/output parameters used in the webservice for obtaining the tag set.

The web service for obtaining the tag set receives the authenticationinformation and the generation number as input parameters and outputsthe generation number and an array structured as the tag set informationto the external control apparatus 124 as an output. FIG. 67 illustratesthe data structure of a tag set.

After step S313, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125, and uses a web servicefor obtaining tags for each tag set obtained in step S313. Theinput/output parameters as showed in FIG. 68 are used in the web servicefor obtaining tags. FIG. 68 illustrates the configuration of theinput/output parameters used in the web service for obtaining tags.

The web service for obtaining tags receives the authenticationinformation, the generation number, and the tag set index number asinput parameters, and outputs the generation number and the arraystructured as a tag to the external control apparatus 124 as outputparameters. FIG. 69 illustrates the data structure of a tag.

Subsequent to step S314, the external control apparatus 124 remotelyaccesses the method provided by the remote interface 125, and uses a webservice for obtaining tag entries for each tag obtained in step S314(step S315). Input/output parameters as showed in FIG. 70 are used inthe web service for obtaining tag entries. FIG. 70 illustrates theinput/output parameters used in the web service for obtaining tagentries.

The web service for obtaining tag entries receives the authenticationinformation, the generation number, the tag index number, filteringcondition, entry offset, and the maximum number of tag entries to beobtained simultaneously as input parameters. On the other hand, the webservice for obtaining tag entries outputs the generation number, thenumber of entries that satisfy the condition, whether all entries thatsatisfy the condition are obtained, and the array of entry informationto the external control apparatus 124. FIG. 71 illustrates the filterconditions. FIG. 72 illustrates the data structure of entry.

In the case of filtering, members showed in FIG. 71 are usable. If aplurality of members are set “on”, it means the logical sum of the “on”members. If “all” is “on”, all entries are obtained whatever the othermembers are. If only “mail addressee” and “user code” are on, entrieshaving mail addresses or usercodes are obtained, for example.

After step S315, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125, and uses a web servicefor obtaining detailed entry information (step S316).

In the case where account information is obtained as the detailed entryinformation, the web service for obtaining account information usesinput/output parameters as showed in FIG. 73. FIG. 73 illustratesinput/output parameters used for the web service for obtaining theaccount information. The web service for obtaining the accountinformation receives the authentication information, the generationnumber, the array of entry ID numbers, and the designation of members tobe obtained from the external control apparatus 124 as input parameters,and outputs the generation number and the array of account informationto the external control apparatus 124 as output parameters. FIG. 74illustrates the data structure of an account. FIG. 75 illustrates thedata structure of a mail address. FIG. 76 illustrates the data structureof facsimile destination information. FIG. 77 illustrates the datastructure of the usercode information.

In the case of obtaining group information as the detailed entryinformation, a web service for obtaining the group information usesinput/output parameters as showed in FIG. 78. FIG. 78 shows theinput/output parameters used in the web service for obtaining groupinformation. The web service for obtaining the group informationreceives as input parameters the authentication information, thegeneration number, the array of entry index numbers, the designatedmember to be obtained from the external control apparatus 124, andoutputs the generation number, the array of group information to theexternal control apparatus 124.

FIG. 79 shows the data structure of the group information, for example.FIG. 80 shows the data structure of the mail group information, forexample. FIG. 81 shows the data structure of the facsimile groupinformation, for example.

After step S316, the external control apparatus 124 creates a screen asshowed in FIG. 92 based on the information obtained in steps S313-S316(step S317). FIG. 92 illustrates the screen created in step S317.

The screen of FIG. 92 has four tabs with which the user can chooseinformation about the number of printed pages by user (CHARGE INFO), theuser restriction by the user (USER RESTRICTION), the e-mail addresses(E-MAIL INFO), and the facsimile addresses (FAX INFO). FIG. 92illustrates the case where the e-mail addresses are displayed.

After step S317, the external control apparatus 124 displays the screencreated in step S317. Since the user information is accessible using theexternal control apparatus 124 instead of the operation panel 70 of themultifunctional apparatus 1, more items of the user information can bedisplayed simultaneously.

The updating of the user information through the remote access will bedescribed by reference to the drawings. After displaying the screen incompliance with the flow chart of FIG. 61, for example, the externalcontrol apparatus 124 remotely accesses the method provided by theremote interface 125 to realize the following: a web service fordisplacing tag information of a tag set, a web service for displacingentries of a tag, a web service for deleting an entry having adesignated ID number, a web service for adding an account, a web servicefor updating account information, a web service for adding a group, aweb service for updating the group information, and so forth.

FIG. 82 shows the input/output parameters used in the web service fordisplacing (replacing) tag information of a tag set for example. The webservice for displacing tag information of a tag set receives as inputparameters the authentication information, the generation number, thetag set control number, and the array of tags from the external controlapparatus 124, and outputs as output parameters the generation numberand the number of displaced tags to the external control apparatus 124.

FIG. 83 shows the input/output parameters used in the web service fordisplacing entries of a tag for example. The web service for displacingentries in a tag receives as input parameters the authenticationinformation, the generation number, the tag index number, the offset, aflag indicating whether all displacements are completed, and the arrayof entry index numbers from the external control apparatus 124, andoutputs as output parameters the generation number and the number ofentries properly processed to the external control apparatus 124.

FIG. 84 shows the input/output parameters used in the web service fordeleting entries having designated ID numbers. The web service fordeleting entries having designated ID numbers receives as inputparameters the authentication information, the generation number, thearray of entry index numbers from the external control apparatus 124,and outputs the generation number and the number of deleted entries asoutput parameters to the external control apparatus 124.

FIG. 85 shows the input/output parameters used in the web service foradding new accounts. The web service for adding new accounts receives asinput parameters the authentication information, the generation number,the array of account information from the external control apparatus124, and outputs as output parameters the generation numbers and thearray of index numbers of added new entries to the external controlapparatus 124.

FIG. 86 shows the input/output parameters used in the web service forupdating account information. The web service for updating the accountinformation receives as input parameters the authentication information,the generation number, the designation of members to be updated, thearray of account information from the external control apparatus 124,and output as output parameter the generation number and the number ofupdated entries to the external control apparatus 124.

FIG. 87 shows the input/output parameters used in the web service foradding new groups. The web service for adding new groups receives asinput parameters the authentication information, the generation number,the array of group information from the external control apparatus 124,and outputs as output parameters the generation number and the array ofindex numbers of added new entries to the external control apparatus124.

FIG. 88 shows the input/output parameters used in the web service forupdating the group information. The web service for updating the groupinformation receives as input parameters the authentication information,the generation number, the designation of members to be obtained, thearray of group information from the external control apparatus 124, andoutputs as output parameters the generation number and the number ofupdated entries to the external control apparatus 124.

Next, the backup and restoring of the user information using remotecontrol will be described below by reference to the drawings. The backupof the user information can be performed by using the access operationto the user information described above. The external control apparatus124 obtains the user information using the access operation of the userinformation, and then stores the obtained user information in a storagedevice so as to backup it.

On the other hand, the restoring of the user information is realized byfollowing the steps described in the flow chart of FIG. 89, for example.FIG. 89 shows a flow chart of the restoring operation of the userinformation using remote control for example.

Since steps S320-S322 are the same as steps S310-S312 of FIG. 61, theirdescription will be omitted.

The external control apparatus 124 remotely accesses the method providedby the remote interface 125 and uses the web service for processingbefore the restoring (step S323).

FIG. 90 shows the input/output parameters used in the web service forprocessing before restoring. The web service for processing beforerestoring receives as input parameters the authentication informationand the generation number from the external control apparatus 124, andoutputs as the output parameter the generation number to the externalcontrol apparatus 124.

After step S323, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125 and uses the web servicefor deleting all entries (step S324). The charge information stored inthe flash memory 65, however, is not deleted.

After step S324, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125 and uses the web servicefor displacing tags in a tag set that is backed up already (step S325).

After step S325, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125 and uses the web servicefor adding all groups that are already backed up (step S326).

After step S326, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125 and uses the web servicefor adding all accounts that are already backed up (step S327).

Subsequent to step S327, the external control apparatus 124 remotelyaccesses the method provided by the remote interface 125 and uses theweb service for displacing entries in a tag that is already backed up(step S328).

After step S328, the external control apparatus 124 remotely accessesthe method provided by the remote interface 125 and uses the web servicefor processing after the restoring (step S329).

FIG. 91 shows the input/output parameters used in the web service forprocessing after the restoring. The web service for processing after therestoring receives as input parameters the authentication informationand the generation number from the external control apparatus 124, andoutputs the generation number to the external control apparatus 124.

Following the steps of FIG. 89, the external control apparatus 124 canrestore the user information stored in the flash memory 65 or the HDD 66using the backup user information. As described above, thanks to theremote interface 125, the user can remotely control the user informationstored in the multifunctional apparatus 1 according to this embodimentof the present invention.

In the case of the configuration showed in FIG. 3, the UCS 49 isincluded in the control service, but the present invention is notlimited to this configuration. The UCS 49 may be provided in theapplication programs 30.

Though the multifunctional apparatus 1 is described in this embodiment,those skilled in the art may recognize that the present invention iseasily applicable to the information processing apparatus 1000. In thecase of the information processing apparatus 1000, the user informationcontrol unit 1260 instead of the UCS 49 controls the user information.In this case, no component corresponding to the SCS 42 is required.

This patent application is based on Japanese priority patentapplications No. 2002-050539 filed on Feb. 26, 2002, No. 2002-050540filed on Feb. 26, 2002, No. 2002-050547 filed on Feb. 26, 2002, No.2003-39974 filed on Feb. 18, 2003, No. 2003-39975 filed on Feb. 18,2003, No. 2003-39976 filed on Feb. 18, 2003, No. 2003-39977 filed onFeb. 18, 2003, No. 2003-39978 filed on Feb. 18, 2003, and No. 2003-39979filed on Feb. 18, 2003, the entire contents of which are herebyincorporated by reference.

1. An image processing apparatus, comprising: an image processinghardware including at least one of a printer unit and a scanner unit;one or more image processing application that processes images using theimage processing hardware; an operating system; and a user informationcontrol program that are commonly accessed and used by the one or moreimage processing application, the user information control programrunning on the operating system, wherein the user information controlprogram, in response to reception of a request from a particular imageprocessing application, provides the particular image processingapplication with user information corresponding to the request.